Moxa DLM On‑Premises v1.2 — Installation & Upgrade Guide

Version 1.2 · 2026

www.moxa.com/products

© 2026 Moxa Inc. All rights reserved.

Moxa DLM On‑Premises has two software components, downloaded as two separate packages on the Moxa website:

• DLM Server — Software Package for DLM Server (runs on a central Ubuntu host; provides the web console & API).
• DLM Agent — Software Package for DLM Agent (runs on each Moxa UC computer; connects the device to the Server).

This single guide covers both. It handles first‑time installation and upgrading from v1.1, and explains how to update the DLM Agent from the DLM Server using Run Custom Script. The parts below are self‑contained, so you can jump straight to the one you need.

Which part do I need?

Release contents & version matrix

DLM components are versioned independently — the Agent version does not match the Server version (this release: Server 1.2.0, Agent 1.1.0 / 2.1.4). Use the table below to pick the correct Agent build for each device.

Part 1: Install the DLM Server

1.1 Prerequisites

• A host running a supported Ubuntu version (see the v1.1 User Manual → Getting Started → System Requirements for current CPU / memory / disk specs).
• The network is configured before installation: server time, DNS, IP, and routing. Incorrect DNS resolution can stop devices from connecting or downloading updates.
• The server installer file dlm-1.2.0-build.88.tar.gz downloaded from the Moxa website.

1.2 Verify the download

A checksum file (dlm-1.2.0-build.88.tar.gz.sha) ships alongside the installer. Verify before installing:

sha1sum -c dlm-1.2.0-build.88.tar.gz.sha
# Expected output:
#   dlm-1.2.0-build.88.tar.gz: OK

1.3 Install (first‑time)

# 1) Set the file name you received
DLM_FILENAME=dlm-1.2.0-build.88.tar.gz

# 2) Extract into /usr/local
sudo tar zxvf ${DLM_FILENAME} -C /usr/local

# 3) Register the local apt repo
echo "deb [trusted=yes] file:/usr/local/moxa-dlm-local-apt-repo jammy/" \
  | sudo tee /etc/apt/sources.list.d/moxa-dlm.list

# 4) Refresh apt and install
sudo apt-get update
sudo apt-get install dlm

The DLM Text User Interface (TUI) opens automatically and runs a system‑requirements check (CPU, memory, disk, OS, package dependencies, network):

Then: 1. Enter the FQDN when prompted (first install only). 2. Create the default administrator account. Default password: admin@123. 3. When done, open the web console at https://YOUR_FQDN.

1B. Upgrade an existing v1.1 Server

Upgrading reuses your existing configuration and keeps all registered devices.

1. Back up the DLM database. DLM has a built-in backup tool (User Manual §8 Backup and Recovery).

   dlm backup                                 # creates an encrypted backup file → dlm-backup-YYYYMMDDxxxx.tgz.enc
   dlm verify-backup dlm-backup-XXXX.tgz.enc  # confirm the backup is valid
   

   Store the encrypted file off the server. For cloud/VM hosts, also take a VM snapshot.

2. Verify the new package (§1.2).

3. Stop the DLM service (required before upgrade):

   sudo systemctl stop dlmg2
   

4. Run the same install commands as §1.3 with the v1.2 file:

   DLM_FILENAME=dlm-1.2.0-build.88.tar.gz
   sudo tar zxvf ${DLM_FILENAME} -C /usr/local
   echo "deb [trusted=yes] file:/usr/local/moxa-dlm-local-apt-repo jammy/" \
     | sudo tee /etc/apt/sources.list.d/moxa-dlm.list
   sudo apt-get update
   sudo apt-get install dlm
   

5. The TUI re‑runs the requirements check and upgrades in place.

1.4 Access the web console

1. Browse to https://YOUR_FQDN.
2. Log in with the administrator email set during install and password admin@123.
3. Change the password immediately on first login.

1.5 Create a Provisioner role (for device enrollment)

DLM ships with no default enrollment account, so before enrolling any device you must create one. Create a low‑privilege Provisioner user for this. A Provisioner can register devices but cannot log in to the web console or API — so the enrollment credentials placed on devices can't be used to reach your data.

1. Users and Roles → Create.
2. Assign the Provisioner role.
3. Create, then hand the email + password to whoever enrolls the Moxa computers.

Part 2: Install the DLM Agent on UC Computers

Before you start (what the Agent needs from the Server)

Whoever installs agents needs three things from the DLM Server side (Part 1):

The device must also be able to reach the Server over the network (ping YOUR_FQDN).

2.1 Choose the right Agent build

Pick the package by your device model and its MIL version. The model is on the device label; to confirm the MIL version, run on the device:

mx-ver -M                 # MIL major version, e.g. 3.4.1  or  4.0.x

2.2 Extract the package — pick the folder for your task

Each Agent package is organised by task, so you use the folder that matches what you want to do:

<agent package>/
├── 1_First_Time_Install/      ← install on a NEW (not yet enrolled) device
│   ├── run                    (guarded install/enroll script)
│   ├── user.yaml              (EDIT: dlmServer.host)
│   ├── credentials.yaml       (EDIT: enrollment account)
│   ├── moxa-dlm-agent_*.deb
│   └── MIL_packages/
├── 2_Update_On_Device/        ← update an ALREADY-enrolled device, locally on the device
│   ├── update_agent.sh        (keeps enrollment & credentials)
│   ├── moxa-dlm-agent_*.deb
│   └── MIL_packages/
├── 3_Update_From_DLM_Server/  ← update from the DLM web console (Run Custom Script)
│   ├── dlm_agent_update.sh
│   └── dlm-agent-update_*.tar (agent + MIL components, ready to upload)
└── Troubleshooting/
    └── collect_dlm_logs.sh

2.3 Edit user.yaml

This file is copied to /etc/moxa/moxa-dlm-agent/user.yaml during install; the Agent reads its settings from there.

# Mandatory
dlmServer:
  host: "demo.dlm.moxa"        # DLM Server FQDN — do NOT include the https:// prefix

# Optional
security:
  skipTLSVerify: true          # see table below

dataTransmission:
  trafficUsageDebug:
    enabled: false
    interval: "10m0s"
  cellularPerformanceDebug:
    enabled: true
    interval: "10m0s"

events:
  cpuTemperature:
    threshold: 0

2.4 Edit credentials.yaml

The account used to enroll the device. There is no default enrollment account — you must first create a Provisioner account on the server (§1.5), then put its email/password here. The values below are placeholders, not real defaults.

email: "provisioner@moxa.com"
password: "provisioner@123"

2.5 (Optional) Validate the server certificate

For higher security, have the device verify the server's identity:

1. In user.yaml, set security.skipTLSVerify: false.
2. Copy the server certificate from the DLM Server to the same folder as run and user.yaml, named cert.pem: /var/lib/dlm/data/certs/root/cert.pem ← on the DLM Server (The installer will refuse to proceed if skipTLSVerify: false but cert.pem is missing.)

2.6 Install on the device

Use the 1_First_Time_Install/ folder. Make sure the device can reach the server (ping YOUR_FQDN).

On the device console, from the 1_First_Time_Install/ folder:

cd 1_First_Time_Install
chmod +x run
sudo ./run

When finished, verify with mx-dlm-agent status (Part 4).

Part 3: Update the DLM Agent

3.1 From the DLM Server (recommended — Run Custom Script)

Use this when the device is already connected to the DLM Server.

1. Open the 3_Update_From_DLM_Server/ folder for the device's model/MIL (§2.1). It contains two files — no extra packaging needed:
   • dlm_agent_update.sh
   • dlm-agent-update_*.tar — agent + MIL components, pre-packaged
2. In the DLM web console, go to All Devices and select the device(s) to update.
3. Click Run custom script.
4. In the dialog, upload dlm_agent_update.sh as the Shell Script and the matching dlm-agent-update_*.tar as the additional file, then click Confirm.

3.2 On the device (local — keeps enrollment)

If the device is not connected to the server (or you prefer a local update), use the 2_Update_On_Device/ folder. It upgrades the agent + MIL components and keeps the existing enrollment and credentials (it does not re-enroll).

On the device console:

cd 2_Update_On_Device
chmod +x update_agent.sh
sudo ./update_agent.sh

Part 4: Verify & Troubleshoot

4.1 Check enrollment status

mx-dlm-agent status

4.2 When status isn't enough

1. Check the service health: systemctl status moxa-dlm-agent Common causes: wrong credentials/password, malformed user.yaml, or a configuration error.
2. If that still doesn't explain it, collect logs for Moxa Support: sudo ./collect_dlm_logs.sh # Produces /tmp/dlm-logs-<host>-<timestamp>.tar.gz — attach it to your support case.

Appendix — quick reference